		Readme.txt file for QLogic QLx24xx/QLE2x0 FCode
				10/19/06


Contents 
------------

1.  OS and Openboot Support
2.  Supported features & Notes
3.  Setting and viewing Fibre Channel connection mode
4.  Setting and viewing Fibre Channel data rate (1,2 or 4 Gigabit)
5   Setting and viewing BIOS compatibility mode
6.  Setting and viewing FCode operation mode
7.  Displaying & entering boot device information (required for qla mode only)
8.  Beacon support
9.  Building a bootable disk
10. Contacting QLogic

==============================================================================

1. OS and Openboot Support 
---------------------------

This driver has been tested with Solaris 10.



==============================================================================

2. Supported Features & Notes
----------------------------- 

* 256 ID Support
* 256 LUN Support
* Fabric boot support
* Local loop boot support
* 1,2 or 4 Gigabit data rate support

Notes: 
1. FCode settings will not be reflected in the CLI or the SANSurfer.
2. Issue Reset-all when change is made to the FCode or Fiber link/target.
3. External Optical Loop back is required when issue test /pci@xxx...
4. Fcode does not support Loop Only connection mode when attached directly to a EMC Symmetrix Storage.


===============================================================================

Selecting QLogic/SUN HBA port from OBP (prior to viewing or setting Fibre Channel connection mode/data rate)
---------------------------------
Example:

(i)ok show-disks
   a) /pci@7c0/pci@0/pci@9/QLGC,qla@0,1/sd  (QLogic HBA Port 1)
   b) /pci@7c0/pci@0/pci@9/QLGC,qla@0/sd    (QLogic HBA Port 0)
   c) /pci@7c0/pci@0/pci@8/QLGC,qla@0/sd
   d) /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk
   e) /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1,1/fp@0,0/disk  (SUN HBA Port 1)
   f) /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/disk    (SUN HBA Port 0)
   g) /pci@7c0/pci@0/pci@1/pci@0/ide@8/cdrom
   h) /pci@7c0/pci@0/pci@1/pci@0/ide@8/disk
   q) NO SELECTION
   Enter Selection, q to quit: f
   /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/disk has been selected.
   Type ^Y ( Control-Y ) to insert it in the command line.
   e.g. ok nvalias mydev ^Y
         for creating devalias mydev for /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1/fp@0,0/disk

(ii)ok " /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@1" select-dev  
  
    or

(ii)ok select /pci@7c0/pci@0/pci@1/pci@0,2/QLGC,qla@0,1

    QLogic QLA2462-Host Adapter Driver(SPARC): 1.22 10/02/06
    Firmware version 4.00.24
   
==============================================================================

3. Setting and viewing Fibre Channel connection mode
-----------------------------------------------------

A. To change or view the current host adapter Fibre Channel connection mode,
   type "set-connection-mode".

   Note: If your Device ID is 54xx (e.g. QLE220, QLE210) then you cannot change
   the connection-mode. By default = Loop preferred, otherwise point-to-point

   Example:
   
   ok set-connection-mode
   Current HBA connection mode: 2 - Loop preferred, otherwise point-to-point
   Do you want to change it? (y/n)
   Choose HBA Connection Mode:
   0 - Loop Only
   1 - Point-to-point only
   2 - Loop preferred, otherwise point-to-point
   Enter: 2
   Current HBA connection mode: 2 - Loop preferred, otherwise point-to-point

==============================================================================

4. Setting and viewing Fibre Channel data rate
-----------------------------------------------
A. To change or view the current host adapter Fibre Channel data rate, type:
   "set-data-rate".

   Note: If your Device ID is 54xx (e.g. QLE220, QLE210) then you cannot change
   the data-rate. By default = Auto-Negotiated.


   Example:
   
   ok  set-data-rate
   Current HBA Data Rate: Auto-Negotiated
   Do you want to change it? (y/n)
   Choose Data Rate:
   0 - 1 Gigabit
   1 - 2 Gigabit
   2 - Auto-negotiated
   3 - 4 Gigabit
   Enter: 2
   Current HBA Data Rate: Auto-Negotiated
      
==============================================================================

5. Setting and viewing BIOS compatibility mode
-----------------------------------------------

This parameter should not be changed unless the following has occurred:
The adapter was shipped with PC BIOS code and Solaris device paths were
created for the attached storage devices. Later the adapter was flashed
with FCode causing a change in the device paths and mount point failures.

If the Solaris devices paths are created with BIOS on the adapter, the device
paths contain "fibre-channel" as in the following example.

/devices/pci@1f,700000/fibre-channel@4

If the adapter is subsequently flashed with FCode the device paths contain
"SUNW,qlc" as in the following example.

/devices/pci@1f,700000/SUNW,qlc@4

If you wish to access the device paths as created when BIOS was present on
the adapter do the following:

1. Select the host adapter device you wish to change as follows -

   ok " /pci@1f,700000/SUNW,qlc@3" select-dev
   
   ok set-mode
   FCode compatibility mode
   Do you want to change it? (y/n)
   Choose Compatibility Mode:
   0 - Fcode
   1 - BIOS
   Enter: 1
   Current compatibility mode: BIOS
   
   ok reset-all

2. Reboot and the device paths have 'fibre-channel' in them.

==============================================================================

6. Setting and viewing FCode operation mode
--------------------------------------------

FCode version 1.15 or later supports two FCode operation modes - qla and qlc.
qla mode requires a driver named qla2300
qlc mode requires a driver named qlc
qla mode is not supported on Sun (SUNW) branded HBAs.

WARNING: Use extreme caution when changing the Fcode Mode as changing it may
cause Solaris to create new device paths for this adapter, which may affect
driver instance numbers and mount points in Solaris

ok set-fc-mode
Current Fcode Mode: qlc
Do you want to change it? (y/n)
Choose Fcode Mode:
0 - qlc
1 - qla
enter: 0
Current Fcode Mode: qlc

==============================================================================

7. Displaying & entering boot device information (required for qla mode only)
------------------------------------------------------------------------------

If the FCode is operation in qla mode the boot device information must be
saved to the HBA as in the example below.

Example showing selection of boot device from list
---------------------------------------------------

{0} ok set-boot-wwn
Current Boot-WWPN = 00000000.00000000  - Boot-LUN =0 - Boot-Target-ID =0
Do you want to change it? (y/n)
Select one of these devices:
0 -  Dev# 0   PortID 101c9    Port WWN 21000020.3711b72b
1 -  Dev# 1   PortID 101ca    Port WWN 21000020.3711c1b6
2 -  Dev# 2   PortID 101cb    Port WWN 21000020.3711c13a
3 -  Dev# 3   PortID 101cc    Port WWN 21000020.3711bc54
4 -  Dev# 4   PortID 101cd    Port WWN 21000020.3711bfb9
5 - Enter Manually
Select #: 2
Enter 16-bit hex Boot ID: 3
Enter 16-bit hex Boot LUN: 0
Current Boot-WWPN = 21000020.3711c13a  - Boot-LUN =0 - Boot-Target-ID =3
{0} ok

Example showing manual entry of boot device information
---------------------------------------------------------

{0} ok set-boot-wwn
Current Boot-WWPN = 21000020.3711c13a  - Boot-LUN =0 - Boot-Target-ID =3
Do you want to change it? (y/n)
Select one of these devices:
0 -  Dev# 0   PortID 101c9    Port WWN 21000020.3711b72b
1 -  Dev# 1   PortID 101ca    Port WWN 21000020.3711c1b6
2 -  Dev# 2   PortID 101cb    Port WWN 21000020.3711c13a
3 -  Dev# 3   PortID 101cc    Port WWN 21000020.3711bc54
4 -  Dev# 4   PortID 101cd    Port WWN 21000020.3711bfb9
5 - Enter Manually
Select #: 5
Enter 64-bit hex Boot WWPN: 1122334455667788
Enter 16-bit hex Boot ID: 99
Enter 16-bit hex Boot LUN: 33
Current Boot-WWPN = 11223344.55667788  - Boot-LUN =33 - Boot-Target-ID =99
{0} ok


==============================================================================  
 
8. Beacon support
------------------
 
Beacon is a feature to allow a specific host adapter to be visually located
easily. When the feature is activated, the yellow and amber LEDs on the back
of the adapter will flash at approximately one second intervals

To enable the feature do the following:
1. Select the host adapter device you wish to locate as follows-

   ok beacon 

   The following message is displayed:

   Flashing adapter LEDs, type any character to quit -

   The yellow and amber LEDs on the selected host adapter will flash until any
   character is entered on the keyboard.

NOTE: For multi-channel host adapters, only one channel's LED will flash.

==============================================================================

9. Building a bootable disk
----------------------------

This procedure assumes the system is already booted from an existing system
disk, and that you have already performed a full system backup.  
The device name shown in this example is for a device on the third PCI bus 
slot, target Id 130, Lun 0, slice 0. The device path is different on 
each system depending on which PCI bus slot, target Id, Lun, etc.

You must have already completed the steps listed above before attempting
to create a bootable disk.

This procedure involves using the Solaris command, ufsdump to create temporary
saveset files for each partition on your current boot disk. In order for this 
method to be successful, you must have enough extra disk space to create the
saveset files or your Solaris machine must have a high capacity tape drive
attached.


1. Determine the amount of disk space used on your current boot disk.  
   Use the '/usr/bin/df -k -l' command for a listing.  

    Example:  /usr/bin/df -k -l

Filesystem            kbytes    used   avail capacity  Mounted on
/dev/dsk/c0t0d0s0    2577118 1650245  875331    66%    /
/proc                      0       0       0     0%    /proc
fd                         0       0       0     0%    /dev/fd
mnttab                     0       0       0     0%    /etc/mnttab
swap                 1310480       0 1310480     0%    /var/run
swap                 1311344     864 1310480     1%    /tmp
/dev/dsk/c0t0d0s7    5135326     114 5083859     1%    /home

This df example shows that the current boot disk is /dev/dsk/c0t0d0s(x).  
There are two partitions of interest, slice 0 or "/" and slice 7 or "/home". 
Slice 0 is using 1.6GB and has 875MB free. Slice 7 uses 114KB and has 5GB
free. Therefore, Slice 7 or "/home" can be used to store the temporary saveset
files. If at least 1.7GB free was not available on this disk,  a partition
would have to be created on the new bootable disk large enough to hold the 
largest temporary saveset plus the largest used space on a partition. In this
example, that would be a partition at least 3.2GB(1.6GB+1.6GB).

2. Use the 'format' command to create, label and format partitions on the 
   new bootable disk. These partitions must be able to contain the contents 
   of the temporary savesets. If you are not familiar with the 'format'
   command, carefully read the Solaris documentation and manual pages for the
   command. Misuse of 'format' could destroy the data on the current disk
   drives.

Example:

format
   partition
      print

Current partition table (original):
Total disk cylinders available: 3880 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders        Size            Blocks
  0       root    wm       0 - 2650        2.73GB    (2651/0/0) 5726160
  1       swap    wu    2651 - 2930      295.31MB    (280/0/0)   604800
  2     backup    wm       0 - 3879        4.00GB    (3880/0/0) 8380800
  3 unassigned    wm       0               0         (0/0/0)          0
  4 unassigned    wm       0               0         (0/0/0)          0
  5 unassigned    wm       0               0         (0/0/0)          0
  6 unassigned    wm       0               0         (0/0/0)          0
  7       home    wm    2931 - 3879     1000.90MB    (949/0/0)  2049840
        
  label
  quit
  quit

3. Use the 'newfs' command to create the file system.

   Example:In case of qla operation mode

   newfs -v /dev/rdsk/c3t130d0s0 (/)

   newfs -v /dev/rdsk/c3t130d0s7 (home) 

   Example:In case of qlc operation mode

   newfs -v /dev/rdsk/c5t22000004CFDF306d0s0 (/)

   newfs -v /dev/rdsk/c5t22000004CFDF306d0s7 (home)
   
   NOTE: The target device Id (t130) is in decimal! The hexadecimal value
   for the target Id is used in the boot command line shown in step 11.

4. Mount the boot partition to the /mnt mount point.

   Example:In case of qla operation mode

   mount /dev/dsk/c3t130d0s0 /mnt

   Example:In case of qlc operation mode

   mount /dev/dsk/c5t22000004CFDF306d0s0 /mnt

5. Cd to the root partition mount point.
 
   Example:
   cd /mnt
   
6. Use the 'ufsdump' utility to copy the root partition to the new boot disk.

   Example: (Same in both qla and qlc operation mode)
 
   ufsdump  0f  -   /  | ufsrestore  rf  -

7. rm restoresymtable

8. Install the boot block on the new boot disk.

   Example:In case of qla operation mode

   installboot  /usr/platform/`uname -i`/lib/fs/ufs/bootblk
      /dev/rdsk/c3t130d0s0

   Example:In case of qlc operation mode

   installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk
   /dev/rdsk/c5t22000004CFDF306d0s0

9. Edit the new vfstab file to properly mount the new partition(s) during 
   boot. In this case each reference to c0t0d0s0 would be changed to 
   c3t130d0s0(qla mode) or c5t22000004CFDF306d0s0(qlc mode).

   Example:
   vi /mnt/etc/vfstab

   NOTE: Replace every instance of c0t0d0 with c3t130d0 (in case of qla 
	operation mode) or c5t22000004CFDF306d0 (in case of qlc operation
	 mode) in the /mnt/etc/vfstab file.


10.Edit the /kernel/drv/sd.conf to add the boot target id and LUN # 
   Example:
   name="sd" class="scsi" target=16 lun=6;
    

11. Shutdown the system.

    Example:
    /sbin/init 0

12. Boot from the newly created boot disk.

    In case of qla operation mode

    Example:
    boot /pci@if,2000/QLGC,qla@1/sd@3,0

    In case of qlc operation mode

    Example:
    boot /pci@1f,700000/SUNW,qlc@3/fp@0,0/disk@w22000004cfdf306 (In case of JBOD)
    
    boot /pci@1f,700000/SUNW,qlc@3/fp@0,0/disk@w216000c0ff898d16,1(Lun No.) (In case of RAID)



13. View the current dump device setting. 

    # dumpadm 
    Dump content: kernel pages
    Dump device: /dev/dsk/c0t0d0s1 (swap)
    Savecore directory: /var/crash/saturn
    Savecore enabled: yes  

   
14. Change the dump device to the swap area of the new boot drive.

    Example: In case of qla operation mode

    # dumpadm -d /dev/dsk/c3t130d0s1
    
    Example: In case of qlc operation mode

    # dumpadm -d /dev/dsk/c5t22000004cfdf306d0s1

    NOTE: The following two steps set the newly created boot disk to be the
	 default boot disk.

    These steps are performed at the system OBP (ok) prompt.

15. Create an alias entry for the new boot device (optional).

    Example: (in OBP at the ok prompt)
    nvalias fibredisk /pci@1f,700000/SUNW,qlc@3/fp@0,0/disk@w22000004cfdf306
    
16. Set default boot device to be the new boot device (optional).

    Example:
    ok setenv boot-device fibredisk


10. Contacting QLogic
-----------------------------

Please visit QLogic's website (http://www.qlogic.com). On this site 
you will find product information, our latest drivers and links for 
technical assistance if needed.

==============================================================================

     Copyright (c) 2000 - 2006 QLogic Corporation. All rights reserved.
